 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| ? semiconductor components industries, llc, 2016 september, 2017 ? rev. 4 1 publication order number: tcc ? 303/d tcc-303 three-output ptic control ic introduction tcc ? 303 is a three ? output high ? voltage digital to analog control ic specifically designed to control and bias on semiconductor?s passive tunable integrated circuits (ptics). these tunable capacitor control circuits are intended for use in mobile phones and dedicated rf tuning applications. the implementation of on semiconductor?s tunable circuits in mobile phones enables significant improvement in terms of antenna radiated performance. the tunable capacitors are controlled through a bias voltage ranging from 1 v to 24 v. the tcc ? 303 high ? voltage ptic control ic has been specifically designed to c over this need, providing three independent high ? voltage outputs that control up to three different tunable ptics in parallel. the device is fully controlled through a mipi rffe digital interface. key features ? controls on semiconductor?s ptic tunable capacitors ? compliant with timing needs of cellular and other wireless system requirements ? 28 v integrated boost converter with three 24 v programmable dac outputs ? low power consumption ? mipi rffe interfaces (1.8 v) ? available in wlcsp (rdl ball arrays) ? compliant with mipi 26 mhz read ? back ? this is a pb ? free device typical applications ? multi ? band, multi ? standard, advanced and simple mobile phones ? tunable antenna matching networks ? compatible with closed ? loop and open ? loop antenna tuner applications www. onsemi.com see detailed ordering and shipping information on page 31 of this data sheet. ordering information marking diagram wlcsp12 case 567mw t33x alyw t33x= specific device code x = a or b a = assembly location l = wafer lot y = year w = work week = pb ? free package (note: microdot may be in either location)
tcc ? 303 www. onsemi.com 2 figure 1. control ic functional block diagram vio vdda l_boost vhv vreg gnd_boost clk data outa 7 bit dac otp level shifter vio por vreg por start reference interface registers booster outb 7 bit dac regulator 4 bit dac bandgap gnd atest vio_on por_vreg 7 7 ibias_start / vref_start vio vdda vreg vhv rc osc level shifter outc 7 bit dac 7 figure 2. rdl padout, bump side view (left), pcb footprint (right), with rdl bump assignment a1 b1 c1 a2 b2 c2 a3 b3 c3 d1 d2 d3 a1 outc a2 vreg a3 vhv b1 outb b2 atest b3 l_boost c1 outa c2 gnd c3 vdda d1 vio d2 data d3 clk tcc ? 303 www. onsemi.com 3 rdl pin out table 1. pad descriptions rdl name type description a1 outc aoh high voltage output c a2 vreg ao regulator output a3 vhv aoh / aih boost high voltage can be forced externally b1 outb aoh high voltage output b b2 atest ao analog test out (note 1) b3 l_boost aoh boost inductor c1 outa aoh high voltage output a c2 gnd p ground c3 vdda p analog supply d1 vio p digital io supply d2 data dio mipi rffe digital io d3 clk di mipi rffe clock legend: pad types aih= high voltage analog input ao= analog output aoh= high voltage analog output di= digital input dio= digital input/output (io) p= power 1. to be grounded in normal operation. electrical performance specifications table 2. absolute maximum ratings symbol parameter rating unit vdda analog supply voltage ? 0.3 to +5.5 v vio io reference supply voltage ? 0.3 to +2.5 v v i/o input voltage logic lines (data, clk) ? 0.3 to vio + 0.3 v v hvh vhv maximum voltage ? 0.3 to 30 v v esd (hbm) human body model, jesd22 ? a114, all i/o 2,000 v v esd (mm) machine model, jesd22 ? a115 200 v t stg storage temperature ? 55 to +150 c t amb_op_max max operating ambient temperature without damage +110 c stresses exceeding those listed in the maximum ratings table may damage the device. if any of these limits are exceeded, device function ality should not be assumed, damage may occur and reliability may be affected. tcc ? 303 www. onsemi.com 4 table 3. recomended operating conditions symbol parameter rating unit min typ max t amb_op operating ambient temperature ? 30 ? +85 c t j_op operating junction temperature ? 30 ? +125 c vdda analog supply voltage 2.3 ? 5.5 v vio io reference supply voltage 1.62 ? 1.98 v functional operation above the stresses listed in the recommended operating ranges is not implied. extended exposure to stresse s beyond the recommended operating ranges limits may affect device reliability. table 4. dc characteristics (t a = ? 30 to +85 c; v outx = 15 v for each output; 2.3 v tcc ? 303 www. onsemi.com 7 vdda power ? on reset (por) upon application of vdda, tcc ? 303 will be in shutdown mode. all circuit blocks are off and the chip draws only minimal leakage current. vio power ? on reset and startup conditions a high level on vio places the chip in startup mode which provides a por to tcc ? 303. por resets all registers to their default settings as described in register content details. vio por also resets the serial interface circuitry. por is not a brown ? out detector and vio needs to be brought back to a low level to enable the por to trigger again. table 7. vio power ? on reset and startup register default state for vio por comment dac boost [1011] vhv = 24 v power mode [01]>[00] transitions from shutdown to startup and then automatically to active mode dac enable [000] v out a, b, c disabled dac a output in high ? z mode dac b output in high ? z mode dac c output in high ? z mode vio shutdown a low level at any time on vio places the chip in shutdown mode in which all circuit blocks are off. the contents of the registers are not maintained in shutdown mode. table 8. vio thresholds (vdda from 2.3 v to 5.5 v; t a = ?30 to +85 c unless otherwise specified) parameter description min typ max unit comments viorst vio low threshold ? ? 0.2 v when vio is lowered below this threshold level the chip is reset and placed into the shutdown mode power supply sequencing the vdda input is typically directly supplied from the battery an d thus is the first on. after vdda is applied and before vio is applied to the chip, all circuits are in the shutdown mode and draw minimum leakage currents. upon application of vio, the chip automatically starts up using default settings and is placed in the active state waiting for a command via the serial interface. table 9. timing (vdda from 2.3 v to 5.5 v; v io = 1.8 v; t a = ?30 to +85 c; out a, out b, out c; chv = 47 nf; l boost = 15 h; vhv = 20 v; turbo ? charge mode off unless otherwise specified) parameter description min typ max unit comments t por_vreg internal bias settling time from shutdown to active mode ? 50 120 s for info only t boost_start time to charge chv @ 95% of set vhv ? 130 ? s for info only t sd_to_act startup time from shutdown to active mode ? 180 300 s t set+ timing for a 2 v to 16 v transition, measured when voltage reaches within 5% of target voltage, mea- sured between the r (5.6 k ) and c (2.7 nf) of an equivalent ptic series load. ? 50 60 s voltage settling time connected on v out a, b, c t set ? timing for a 16 v to 2 v transition, measured when voltage reaches within 5% of target voltage, mea- sured between the r (5. 6 k ) and c (2.7 nf) of an equivalent ptic series load. ? 50 60 s effective ptic tuning voltage settling time, measured between an equivalent r and c ptic load t set+ output a, b, c positive settling time with turbo ? 35 ? s voltage settling time connected on v out a, b, c t set ? output a, b, c negative settling time with turbo ? 35 ? s voltage settling time connected on v out a, b, c tcc ? 303 www. onsemi.com 8 figure 4. output settling diagram fi g ure 5. startu p timin g dia g ram tcc ? 303 www. onsemi.com 9 boost control tcc ? 303 integrates an asynchronous current control boost converter. it operates in a discontinuous mode and features spread ? spectrum circuitry for electro ? magnetic interference (emi) reduction. the average boost clock is 2 mhz and the clock is spread between 0.8 mhz and 4 mhz. boost output voltage (vhv) control principle the asynchronous control starts the boost converter as soon as the vhv voltage drops below the reference set by the 4 ? bit dac and stops the boost converter when the vhv voltage rises above the reference again. due to the slow response time of the control loop, the vhv voltage may drop below the set voltage before the control loop compensates for it. in the same manner, vhv can rise higher than the set value. this effect may reduce the maximum output voltage available. please refer to figure 6 below. the asynchronous control reduces switching losses and improves the output (vhv) regulation of the dc/dc converter under light load, particularly in the situation where tcc ? 303 only maintains the output voltages to fixed values. set vhv figure 6. vhv voltage waveform vhv time delay delay chv discharge delay chv recharge boost running high impedance (high z) feature in shutdown mode the out pins are set to a high impedance mode (high z). following is the principle of operation for the control ic: 1. the dac output voltage v out is defined by: v out dac code 127 24 v (eq. 1) 2. the voltage vhv defines the maximum supply voltage of the dac supply output regulator and is set by a 4 ? bit control. 3. the maximum dac dc output voltage v out is limited to (vhv ? 2 v). dac can achieve higher output voltages, but timing is not maintained for swings above vhv ? 2 v. 4. the minimum output dac voltage v out is 1.0 v max. figure 7. dac output range example a figure 8. dac output range example b digital interface the control ic is fully controlled through a digital interface (data, clk). the digital interface is described in the following sections of this document. turbo ? charge mode the tcc ? 303 control ic has a turbo ? charge mode that significantly shortens the system settling time when changing programming voltages. in turbo ? charge mode the dac output target voltage is temporarily set to either a delta voltage above or a delta voltage below the actual desired target. the delta voltage is 4 volts. after the dac value message is received, the delta voltage is calculated by hardware, and is applied in digital format to the input of the dac, right after trigger is received. the period for which the delta voltage is maintained to the input of the dac, the turbo time, is calculated based on following considerations: tcc ? 303 www. onsemi.com 10 ? dac_timer_a[4:0] / dac_timer_b[4:0] / dac_timer_c[4:0]: these are the dac timer configuration fields. for the turbo mode, they define the turbo latency value, when the target+delta voltage is active. if each dac is updated over and over with the same turbo delay value, these fields do not need to be updated at each dac update. the register has to hold a non ? zero value for a turbo update. ? dac_tc2x_a / dac_tc2x_b / dac_tc2x_c: if these bits are set, the timer loads dac_timer_x * 2 value as opposed to dac_timer_x value. this allows a turbo operation delay up to 124 s. ? dac_tcm_a [1:0] / dac_tcm_b [1:0] / dac_tcm_c [1:0] : if the turbo direction is down and the turbo target is below 4 v, these multiplication factors are utilized to extend the turbo delay. further formula provided below. ? gl_a / gl_b / gl_c: these are the dac update mode configuration fields, which need to be set to turbo mode at the new dac value update and prior to the sw trigger (optional). these bits are part of the dac value register. if they are set to 0, the dac is in turbo mode, as long as the corresponding dac_timer register is non ? zero. a dac_timer =0 means an immediate update independent of the gl_a/b/c value. ? the turbo up or down voltage is decided based on the comparison of the new dac value and the old dac value. if the new value is greater, the turbo direction will be up. otherwise it will be down. in case of both dac values being equal, there is no dac update applied.after a turbo request is received, any trigger will start the turbo output transition. the trigger could be: ? a mipi ? rffe software trigger controlled by rffe_pm_trig register ? an internal generated trigger after the corresponding dac value is updated, as described in section dac update triggering. the dac values send by digital turbo ? charge logic to dacs are: ? during turbo ? charge delay duration the value applied is ?dac_new 4 v? (the polarity of the 4 v turbo will depend on if turbo charge is up or down) ? if dac_new > dac old, and dac_new+4 v is exceeding the word length of the dac, it is saturated to max value possible. ? if dac_new < dac_old, and dac_new ? 4 v is a negative number, a dac value of 0 is applied. ? after turbo ? charge delay duration the value applied is the actual dac_new. tcc ? 303 www. onsemi.com 11 table 10. dac_timer_a/b/c unit delays dac_timer_a/b/c [4:0] turbo delay time in turbo mode or glide step duration in glide mode [ s] bit 4 bit 3 bit 2 bit 1 bit 0 0 0 0 0 0 immediate update 0 0 0 0 1 2 0 0 0 1 0 4 0 0 0 1 1 6 0 0 1 0 0 8 0 0 1 0 1 10 0 0 1 1 0 12 0 0 1 1 1 14 0 1 0 0 0 16 0 1 0 0 1 18 0 1 0 1 0 20 0 1 0 1 1 22 0 1 1 0 0 24 0 1 1 0 1 26 0 1 1 1 0 28 0 1 1 1 1 30 1 0 0 0 0 32 1 0 0 0 1 34 1 0 0 1 0 36 1 0 0 1 1 38 1 0 1 0 0 40 1 0 1 0 1 42 1 0 1 1 0 44 1 0 1 1 1 46 1 1 0 0 0 48 1 1 0 0 1 50 1 1 0 1 0 52 1 1 0 1 1 54 1 1 1 0 0 56 1 1 1 0 1 58 1 1 1 1 0 60 1 1 1 1 1 62 the value of turbo delay time is deducted based on the hardware comparison of new dac value in respect to old dac value, as follows. in this calculation the decimal ?21? value corresponds to 4 v dac drive. as the dac new value is closer to 0 v in a down turbo, the delay time increases more. if dac new > dac old, then t up = dac_timer_a/b/c << dac_tc2x_a/b/c if dac new < dac old, and dac new < 21, then t down = dac_timer_a/b/c << dac_tc2x_a/b/c + dac_tcm_a/b/c * (21 ? dac new) if dac new < dac old, and dac new > 21, then t down = dac_timer_a/b/c << dac_tc2x_a/b/c if dac new < dac old, and dac new = 21, then t down = dac_timer_a/b/c << dac_tc2x_a/b/c table 1 1. turbo ? charge multiplication factor tcm [1:0] multiplication factor 00 (default) 4 01 3 10 2 11 1 tcc ? 303 www. onsemi.com 12 transition from turbo to turbo or immediate update in the event a new trigger is received during a turbo transition, the ongoing turbo operation is halted and the new dac value is applied immediately. there won?t be any turbo and the hi_slew is kept low. transition from turbo to glide in the event that a new glide transition is triggered during a turbo event, then the turbo process is stopped and the current target value is set at the dac output immediately without hi_slew. the new glide is started from this value. dac disable during turbo (including active to low power mode transition) if the dac, which is in t urbo is disabled, the target dac value is immediately applied without hi_slew. the dac does not continue with the turbo when it is re ? enabled. glide mode the tcc ? 303 control ic has a glide mode that significantly extends the system transition time when changing programming voltages. glide mode is controlled by the following registers: ? dac_timer_a[4:0] / dac_timer_b[4:0] / dac_timer_c[4:0]: these are the dac timer configuration fields. for the glide mode they define the step duration. if each dac is updated over and over with the same glide step, these fields do not need to be updated at each dac update. the register has to hold a non ? zero value for a glide update. ? gl_a / gl_b / gl_c: these are the dac update mode configuration fields, which need to be set to glide mode at the new dac value update and prior to the sw trigger (optional) . these bits are part of the dac value register. if they are set to 1, the dac is in glide mode, as long as the corresponding dac_timer register is non ? zero. a dac_timer =0 means an immediate update independent of the gl_a/b/c value. after a glide request is received, any trigger will start the glide output transition. the trigger could be: ? a mipi ? rffe software trigger controlled by rffe_pm_trig register ? an internal generated trigger after the corresponding dac value is updated, as described in a later section. immediately after the trigger, the dac_old value is loaded in the msb?s of the upper byte of a 15 bit accumulator, while the lower byte of accumulator is being reset to 0x00. at the same time a count step is calculated: glide_step[6:0] = dac_new ? dac_old; if dac_new > dac_old glide_step[6:0] = dac_old ? dac_new; if dac_new < dac_old accumulator[14:0] = dac_old, 0x00; note: glide is disabled if dac_new = dac_old. from the moment the trigger is received, a tick is generated internally, with a frequency controlled by the dac_timer_a/b/c registers. each dac has its own tick generator running independently of the other dac. each time a trigger is received for a dac, the setting of the dac_timer_a/b/c register is sampled in a counter dedicated to that dac. any update of the dac_timer_a/b/c register after trigger is received will be ignored until the next trigger is received each time a tick is generated, the content of the accumulator is either incremented or decremented, depending whether dac_new is either bigger or smaller than dac_old. accumulator[14:0] = accumulator[14:0] + glide_step; if dac_new > dac_old accumulator[14:0] = accumulator[14:0] ? glide_step; if dac_new < dac_old each time a tick is generated, the output of the dac[6:0] is updated with the value of accumulator[14:8]; the gliding process continues until, upper 7 bits of the accumulator matches the value of the dac_new. accumulator[14:8] dac_new, when dac_new > dac_old accumulator[14:8] dac_new, when dac_new < dac_old the glide timer will reference the 2 mhz clock divided to provide between 2 s and 62 s per glide step. each dac is independent in terms of its switching operation, thus each dac may be independently programmed for normal, turbo or glide regardless of the switching operation of the other dacs. use ? case hint: in a scenario where the turbo delay needs to be set to 54 us and the glide should be taking ~7 ms, the dac_timer can be configured as 7000/256 = 27 s and the dac_tc2x configuration can be set. this way the timer value would not need to be updated during the glide ? turbo switches, and only the gl_x bit in dac value update needs to be toggled. transition from glide to glide in the event a new glide request is received during a glide transition, the ongoing glide operation is halted and the new glide operation is started from the dac value, where the previous glide has left off. the dac timers can be updated to a new value at the trigger. transition from glide to turbo or normal switching in the event that a new normal switching or turbo dac value is received during a glide transition, then the glide process is stopped and the dac immediately switches to the newly received target value without turbo or glide. the hi_slew is not applied. dac disable during glide (including active to low power mode transition) if the dac, which is gliding is disabled, the dac value holds on to the value where the glide stops. the dac does tcc ? 303 www. onsemi.com 13 not continue with the glide when it is re ? enabled. it drives the last calculated dac value without a hi_slew. dac update triggering the entire digital logic responsible for dac updates is using the clock provided by the internal rc oscillator. in order to minimize the power consumption, the rc clock is set at a low frequency around 2 mhz. dac writes figure 9 shows the diagram of the dac data path, from the moment data is written into dacx_value register, until it is sent out to dac. after the dacx_value register is written using mipi ? rffe clock, the data is copied on rc clock domain, into the first data stage represented in figure 9 as ?completed?. the data is moved into ?new? and ?dac ? out? stages by the dac driver state machine, once the trigger is detected. the turbo path also highlights the glide calculation. if sw trigger is not enabled, then data will flow through the stages right after the corresponding dac is updated, without waiting for a trigger (mipi write is considered as the trigger). figure 9. dacx data path to bypass the sw trigger and enable an immediate trigger the mask bits under the rffe_pm_trig register should be set according to the usid control of the dac. trigger mask 2 is controller with usid_2, trigger mask 1 is controlled with usid_1 and trigger mask 0 is controlled with usid_0. in mipi ? rffe configuration, if rffe_pm_trig / trigger_mask_2 = ?1?, and rffe_pm_trig / trigger_mask_1 = ?1? and rffe_pm_trig / trigger_mask_0 = ?1? (all software triggers are masked), then each dac value is copied into ?completed? stages of each dac, after the messages rffe_reg_0x06, rffe_reg_0x07 or rffe_reg_0x08 respectively are received, as shown in following sequence. mipi_rffe_write #1: send dac_a_value and glide/turbo mode to rffe_reg_0x06 mipi_rffe_write #2: send dac_b_value and glide/turbo mode to rffe_reg_0x07 mipi_rffe_write #3: send dac_c_value and glide/turbo mode to rffe_reg_0x08 the individual writes above could be combined into a single extended write with all dacs controlled with the same usid or the durs of the dacs are sitting at ?11? configuration. right after mipi_rfee_write #1 to rffe_reg_0x06, above, is received the dac_a value register is copied in ?completed? stage of dac_a. the timers do not need to be updated for each dac update. but if they need to be, they can be updated as part of a full extended write or single write prior to the dac value updates without any timing limitation. since the sw trigger is masked, next rc clock cycle after dac values are copied in ?completed? stage, the data will move in next stages ?new? and ?dac ? out? without waiting for any trigger. the similar events occur for dac_b and dac_c after the mipi_rfee_write #2 and mipi_rfee_write #3. due to the fact that the mipi ? rffe master can send dac updates messages at a higher frequency, than rc clock, the data buffer ?completed?, can be overwritten if new dac updates occur in the same time when the buffer is loaded. while data and configuration are copied from dacx_value register into ?completed? stage, the mipi ? rffe master must not send any new dac updates to dacx_value registers or configurations. the time required tcc ? 303 www. onsemi.com 14 for the data to be copied from dacx_value register into ?completed? stage is max 1500 ns, which is defined by the three rc clock cycles required to synchronize data from mipi ? rffe clock domain to rc clock domain. in figure 10, dac_upda te_lat represents the period when mipi ? rffe master is not allowed to send any new dac updates to dacx_value registers and dac configuration registers. the dac enables (rffe_reg_0x00) and booster configurations (rffe_reg_0x02) are applied immediately without waiting any trigger. these registers should be configured prior, so that the dac updates are effective as fast as possible. in test mode the hi_slew settings are sampled at the trigger similar to the dac_timers. figure 10. dac_update_lat requirement the sw trigger as well as immediate trigger can be configured in many combinations using the dur settings of the dacs and the usid values. the sw trigger masks can only be changed with the write access using the slave address of their corresponding usid. but the corresponding triggers can be set by accesses over broadcast, with broadcast id (0x0) or gsid. the triggering and dac register access is governed by these rules: ? the dur configuration assigns a dac to a usid. the corresponding dac registers can only be accessed with usid defined by its dur. ? the immediate update of this dac is enabled if the sw trigger mask of the corresponding usid is set (disabled). ? the pm_trig register bit0 (sw trigger0) is masked by bit4 and assigned to dacs triggering, which are mapped to usid0 or all usids (the dac dur=0 or 3). ? the pm_trig register bit1 (sw trigger1) is masked by bit5 and assigned to dacs triggering, which are mapped to usid1 or all usids (the dac dur=1 or 3). ? the pm_trig register bit2 (sw trigger2) is masked by bit6 and assigned to dacs triggering, which are mapped to usid2 or all usids (the dac dur=2 or 3). ? for a dac with dur=3, all sw masks need to be set for that dac to be triggered with direct access to its target register. if all dacs are kept at dur values of 3 and the usids are kept the same (reset condition), the part behaves according to the mipi spec with single usid. if some of the usids are different while dur=3, the part responds to the accesses with these different usids the same fashion. if all usids are kept equal, the part functions with a single usid. but the dur settings still control the sw trigger mapping for the dacs independent of the usid values. the dacs which are not holding a dur value of 3 will be under the control of the sw trigger ? mask duo mapped by their dur setting. in table 12 some example register settings for listed functionality are provided. for the given functionality the response of the part to dac updates and sw triggers are tabulated. in this table the ?dac trigger? corresponds to a trigger happening at the time of the dac value update. the ?sw trigger? corresponds to a trigger happening with the pm_trig register write. at this point, it is assumed that the dacs are enabled and the new dac value is not matching to the existing pre ? triggered dac value in the active register. some of the abbreviations utilized in the table are: trg = successful trigger of the new targets hld = no trigger, hold on to existing dac drives wr = the new dac values are captured into rffe shadow registers nw = the rffe write to shadow registers are blocked, no register update. tcc ? 303 www. onsemi.com 15 table 12. immediate vs software triggering using usids and durs functionality & exam- ple register values daca wr id0 daca wr id1 daca wr id2 daca wr broad trigger 3b111 id0 trigger 3b111 id1 trigger 3b111 id2 trigger 3b111 broad trigger 3b001 broad trigger 3b010 broad trigger 3b100 broad comments (default) dac trigger ? single usid ? dur=3 dur_a = 3 (usidx, trgx) sw ? trg mask = 3?b111 usid0,1,2 = 4b0111 trg (wr) trg (wr) trg (wr) hld (nw) hld hld hld hld hld hld hld all usids are the same. all sw triggers are masked. the usid dac writes trig- ger immediately. sw trigger ? single usid ? dur =3 dur_a = 3 (usidx, trgx) sw ? trg mask = 3?b101 usid0,1,2 = 4b0111 hld (wr) hld (wr) hld (wr) hld (nw) trg trg trg trg hld trg hld all usids are the same. only trigger 1 is enabled. this enables the sw trig- ger since dur=3, mapping the dac to all triggers dac trigger ? single usid ? dur=0 dur_a = 0 (usid0, trg0) sw ? trg mask = 3?b101 usid0,1,2 = 4b0111 trg (wr) trg (wr) trg (wr) hld (nw) hld hld hld hld hld hld hld all usids are the same. only trigger 1 is enabled. the dur of the dac is mapping it to trigger 0 (masked). therefore sw trigger is disabled. sw trigger ? single usid ? dur =1 dur_a = 1 (usid1, trg1) sw ? trg mask = 3?b101 usid0,1,2 = 4b0111 hld (wr) hld (wr) hld (wr) hld (nw) trg trg trg trg hld trg hld all usid?s are the same. only trigger 1 is enabled. the dur of the dac is mapping it to trigger 1 (en- abled). therefore sw trig- ger is enabled. dac trigger ? (1,2) usids ? dur=2 dur_a = 2 (usid2, trg2) sw ? trg mask = 3?b100 usid0,1 = 4b0111, usid2 = 4b1000 hld (nw) hld (nw) trg (wr) hld (nw) hld hld hld hld hld hld hld usid2 is different, only usid2 dac access is al- lowed and the dac trig- gers immediately, since the sw trigger mask is set. sw trigger ? (1,2) usids ? dur =2 dur_a = 2 (usid2, trg2) sw ? trg mask = 3?b000 usid0,1 = 4b0111, usid2 = 4b1000 hld (nw) hld (nw) hld (wr) hld (nw) hld hld trg trg hld hld trg usid2 is different, only usid2 dac access is al- lowed. trigger 2 is un- masked, sw trigger is en- abled. only trigger 2 is ac- tive for usid2. dac trigger ? (2,1) usids ? dur = 1 dur_a = 1 (usid1, trg1) sw ? trg mask = 3?b110 usid0,1 = 4b0111, usid2 = 4b1000 trg (wr) trg (wr) hld (nw) hld (nw) hld hld hld hld hld hld hld since usid0 = usid1 both usid0, usid1 dac target writes are allowed. sw trigger1 masked; sw trig- gering disabled sw trigger ? (2,1) usids ?dur = 1 dur_a = 1 (usid1, trg1) sw ? trg mask = 3?b100 usid0,1 = 4b0111, usid2 = 4b1000 hld (wr) hld (wr) hld (nw) hld (nw) trg trg hld trg hld trg hld same as above but sw trigger 1 is enabled; sw triggering enabled. usid0, usid1 are the same but the dac is mapped to trg1 only. trg0 alone does not trigger. dac trigger ? (1,1,1) usids ? dur = 0 dur_a = 0 (usid0, trg0) sw ? trg mask = 3?b001 usid0 = 4b0111, usid1 = 4b1000, usid2 = 4b1001 trg (wr) hld (nw) hld (nw) hld (nw) hld hld hld hld hld hld hld the dac is mapped to usid0 and the corre- sponding trigger is masked. it triggers imme- diately at dac update with usid0 sw trigger ? (1,1,1) usids ? dur = 0 dur_a = 0 (usid0, trg0) sw ? trg mask = 3?b000 usid0 = 4b0111, usid1 = 4b1000, usid2 = 4b1001 hld (wr) hld (nw) hld (nw) hld (nw) trg hld hld trg trg hld hld the dac is mapped to usid0 and the trg0 is enabled. it triggers only at trg0 with usid0 or broadcast access tcc ? 303 www. onsemi.com 16 mipi rffe interface tcc ? 303 is a slave device and is fully compliant to the mipi alliance specification for rf front ? end control interface (rffe) version 1.10.00. following mipi rffe commands are supported: 1. register 0 write 2. register write 3. register read 4. extended register write 5. extended register read registers 0x00 to 0x1f are available to be read/written. at full ? speed read with heavy load, the rffe read mode bit rffe_rdm can be configured to ?1?, to shift the data capture to falling edge. otherwise it is recommended to keep this bit in its default state, since the falling edge read data capture is a violation for rffe interface standard. the violation is due to the toggling during the 2 nd half of the bus park cycle, which could create bus contention with the master. the extended register write long and read long commands are not supported. if an extended register write long command is received, no register is written and the rffe_status.wure flag is set. if an extended register read long command is received, the part responds with bus idle and the rffe_status.rure flag is set. the read access to registers rffe_reg_0x03 to rffe_reg_0x08 returns the active register content, which is the register updated after a trigger. the pre ? trigger shadow register does not have read access. table 13. mipi rffe interface specification (t a = ? 30 to +85 c; 2.3 v < vdda < 5.5 v; 1.1 v < v io < 1.8 v; unless otherwise specified) parameter description min typ max unit comments f sclk clock full ? speed frequency 0.032 ? 26 mhz full ? speed operation: 1.65 v < v io < 1.95 v t sclk clock full ? speed period 0.038 ? 32 s full ? speed operation: 1.65 v < v io < 1.95 v t sclkih clk input high time 11.25 ? ? ns full ? speed t sclkil clk input low time 11.25 ? ? ns full ? speed v tp positive going threshold voltage 0.4 x vio ? 0.7 x vio v clk, data, 1.2 or 1.8 v bus v tn negative going thresh- old voltage 0.3 x vio ? 0.6 x vio v clk, data, 1.2 or 1.8 v bus v h hysteresis voltage (v tp ? v tn ) 0.1 x vio ? 0.4 x vio v clk, data, 1.2 or 1.8 v bus i ih input current high ? 2 ? +10 a sdata = 0.8 x vio ? 1 ? +10 a sclk = 0.8 x vio i il input current low ? 2 ? +1 a sdata = 0.2 x vio ? 1 ? +1 a sclk = 0.2 x vio c clk input capacitance ? ? 2.2 pf clk pin c data input capacitance ? ? 2.5 pf data pin td setup write data setup time ? ? 1 ns full ? speed td hold write data hold time ? ? 5 ns full ? speed t read_access read data valid from clk rising edge ? ? 7.11 ns full speed at v io = 1.80 v, +25 c, and max 15 pf load on data pin t read_access read data valid from clk rising edge ? ? 9.11 ns full speed at v io = 1.80 v, +25 c, and max 50 pf load on data pin tcc ? 303 www. onsemi.com 17 figure 11. mipi ? rffe signal timing during master writes to ptic control ic clk data td setup td hold td setup td hold figure 12. mipi ? rffe signal timing during master reads from ptic control ic figure 13. bus park cycle timing when mipi ? rffe master reads from ptic control ic clk data t read_access t sdataotr t sdataotr t read_access clk data bus park cycle t sdataz tcc ? 303 www. onsemi.com 18 the control ic contains eighteen 8 ? bit registers. register content is described in table 14. some additional registers implemented as provision, are not described in this document. table 14. mipi rffe address map address description usid purpose access size [bits] 0x00 rffe_reg_0x00 all dac enables r/w regwrite0 8 0x01 rffe_reg_0x01 all dur for dac_a/_b/_c r/w 8 0x02 rffe_reg_0x02 all booster settings r/w 8 0x03 rffe_reg_0x03 dur_a dac_a timer setup r/w 8 0x04 rffe_reg_0x04 dur_b dac_b timer setup r/w 8 0x05 rffe_reg_0x05 dur_c dac_c timer setup r/w 8 0x06 rffe_reg_0x06 dur_a used to set up / trigger out a r/w 8 0x07 rffe_reg_0x07 dur_b used to set up / trigger out b r/w 8 0x08 rffe_reg_0x08 dur_c used to set up / trigger out c r/w 8 0x09 rffe_reg_0x09 all rffe read mode control r/w 8 0x09 to 0x17 spare n/a spare for future product development r/w 8 0x18 usid_1 usid_1 & broadcast spare [7:6] [5,4] = manufacturer id [9:8] usid_1 [3:0] r/w 8 0x19 usid_2 usid_2 & broadcast spare [7:6] [5,4] = manufacturer id [9:8] usid_2 [3:0] r/w 8 0x1a rffe_status all rffe status register r/w 8 0x1b rffe_group_sid all the group broadcast id r/w 8 0x1c rffe_pm_trig all & broadcast power mode & trigger control pwr_mode [7:6] trig_reg [5:0] r/w 8 0x1d pid_0, default all mipi product id (note 2) r 8 0x1e manufacturer id register all mn (10bits long) manufacturer id[7:0] (note 2) r 8 0x1f usid_0, default usid_0 & broadcast spare [7:6] [5,4] = manufacturer id [9:8] (note 3) usid [3:0] r/w 8 2. the least significant bits from the product id register are refined by otp. the other seven bits of product id are hardcoded in asic. 3. the manufacturer id is hardcoded in asic, mapped in a read ? only register. register content details register rffe: rffe_reg_0x00 address rffe a[4:0]: [0x00] reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits spare spare spare spare spare dac c en dac b en dac a en reset u ? 0 u ? 0 u ? 0 u ? 0 u ? 0 w ? 0 w ? 0 w ? 0 bit [2:0] each dac is enabled when the corresponding bit is set. the enable or disable occurs immediately without waiting for a trigger. 0: off (default) 1: enabled bit [7]: register 0 write command excludes this bit. the extended writes to this address ignores bit 7. the bit is not utilized . tcc ? 303 www. onsemi.com 19 register rffe: rffe_reg_0x01 address rffe a[4:0]: 0x01 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits spare dur_c [1:0] dur_b [1:0] dur_a [1:0] reset u ? 0 u ? 0 w ? 1 w ? 1 w ? 1 w ? 1 w ? 1 w ? 1 dur_x [1:0] (dac x usid response) ?00?: responds only to usid_0 in dac register write. sw trigger0 mask defines the triggering source. ?01?: responds only to usid_1 in dac register write. sw trigger1 mask defines the triggering source. ?10?: responds only to usid_2 in dac register write. sw trigger2 mask defines the triggering source. ?11?: responds to any 3 usid in dac register write. any trigger mask cleared enables the sw triggering. register rffe: rffe_reg_0x02 address rffe a[4:0]: 0x02 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits boost_clk_en boost_pwm_en spare boost_en boost voltage value reset w ? 1 w ? 1 u ? 0 w ? 1 w ? 1 w ? 0 w ? 1 w ? 1 bit [7]: enables the booster clock. the clock should be disabled when the booster is turned off. bit [6]: enables the boost oscillator pwm function. this signal should be turned off in case the booster generates low voltages to reduce the ripple. bit [4]: enable/disable of the booster. booster must be turned off when the high voltage is provided externally. bit [3:0]: boost voltage value . refer to table 15 for values table 15. boost voltage setting boost voltage value[3:0] vhv [v] note boost voltage value[3:0] vhv [v] note 0000 13 target values 1000 21 target values 0001 14 1001 22 0010 15 1010 23 0011 16 1011 24 (default) 0100 17 1100 25 0101 18 1101 26 0110 19 1110 27 0111 20 1111 28 register rffe: rffe_reg_0x03 address rffe a[4:0]: [0x03] reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits dac_tc2x_a dac_tcm_a dac_timer_a reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if this bit is set, in turbo mode dac_timer * 2 value is loaded into the dac timer. the glide always sets the step dela y to dac_timer value independent of this bit. bit [6:5] it defines the multiplication factor of timer extension when the turbo ? down value is below 4 v. bit [4:0] for the definition of dac_timer field, see table 10. note: the read access to this register will return the active content post ? trigger, not the shadow register. tcc ? 303 www. onsemi.com 20 register rffe: rffe_reg_0x04 address rffe a[4:0]: [0x04] reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits dac_tc2x_b dac_tcm_b dac_timer_b reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if this bit is set, in turbo mode dac_timer * 2 value is loaded into the dac timer. the glide always sets the step dela y to dac_timer value independent of this bit. bit [6:5] defines the multiplication factor of timer extension when the turbo ? down value is below 4 v bit [4:0] for definition of dac_timer field, see table 10. note: the read access to this register will return the active content post ? trigger, not the shadow register. register rffe: rffe_reg_0x05 address rffe a[4:0]: [0x05] reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits dac_tc2x_c dac_tcm_c dac_timer_c reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if this bit is set, in turbo mode dac_timer * 2 value is loaded into the dac timer. the glide always sets the step dela y to dac_timer value independent of this bit. bit [6:5] defines the multiplication factor of timer extension when the turbo ? down value is below 4 v bit [4:0] for definition of dac_timer field, see table 10. note: the read access to this register will return the active content post ? trigger, not the shadow register. register rffe: rffe_reg_0x06 address rffe a[4:0]: 0x06 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits gl_a dac a value [6:0] reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if the gl_a=1, a non ? zero value in dac timer in starts a glide. if gl_a =0 and the dac_timer_a is not zero, t urbo is started with the new dac a value. note: the read access to this register will return the active content post ? trigger, not the shadow register. the dac value read ? back is not the actual analog drive, it is the target level. register rffe: rffe_reg_0x07 address rffe a[4:0]: 0x07 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits gl_b dac b value [6:0] reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if the gl_b=1, a non ? zero value in dac timer in starts a glide. if gl_b =0 and the dac_timer_b is not zero, t urbo is started with the new dac b value. note: the read access to this register will return the active content post ? trigger, not the shadow register. the dac value read ? back is not the actual analog drive, it is the target level. tcc ? 303 www. onsemi.com 21 register rffe: rffe_reg_0x08 address rffe a[4:0]: 0x08 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits gl_c dac c value [6:0] reset w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 w ? 0 bit [7] if the gl_c=1, a non ? zero value in dac timer in starts a glide. if gl_c =0 and the dac_timer_c is not zero, t urbo is started with the new dac c value. note: the read access to this register will return the active content post ? trigger, not the shadow register. the dac value read ? back is not the actual analog drive, it is the target level. register rffe: rffe_reg_0x09 address rffe a[4:0]: 0x09 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits spare spare spare spare spare spare spare rffe_rdm reset u ? 0 u ? 0 u ? 0 u ? 0 u ? 0 u ? 0 u ? 0 w ? 0 bit [0] this bit defines the read capture edge internal to the chip. if 1, the read data is released at the falling edge of the rffe clock. in a system with very heavy load and 26 mhz speed, this bit can be set to gain some time .for speeds below full ? speed and light load, it is recommended to keep this bit cleared to switch to rising edge read data release. register rffe: rffe_usid_1 address rffe a[4:0]: 0x18 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits reserved (2) mpn9 (2) mpn8 (2) usid3 (1) usid2 (1) usid1 (1) usid0 (1) reset 0 0 0 1 w ? 0 w ? 1 w ? 1 w ? 1 usid = unique slave identifier register 1. usid field can be changed by: ? mipi ? rffe broadcast messages when usid field within the register write command is 0b0000 ? mipi ? rffe individual messages when usid field within the register write command equal with content of rffe_reg_0x18[3:0] 2. in the sequence of writing usid field, the upper [7:4] must match the value 0b0001 hardcoded in the rffe register 0x18 note: usid_1 value is not retained during shutdown power mode. register rffe: rffe_usid_2 address rffe a[4:0]: 0x19 reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits reserved (2) mpn9 (2) mpn8 (2) usid3 (1) usid2 (1) usid1 (1) usid0 (1) reset 0 0 0 1 w ? 0 w ? 1 w ? 1 w ? 1 usid = unique slave identifier register 1. usid field can be changed by: ? mipi ? rffe broadcast messages when usid field within the register write command is 0b0000 ? mipi ? rffe individual messages when usid field within the register write command equal with content of rffe_reg_0x19[3:0] 2. in the sequence of writing usid field, the upper [7:4] must match the value 0b0001 hardcoded in the rffe register 0x19 note: usid_2 value is not retained during shutdown power mode. tcc ? 303 www. onsemi.com 22 register rffe: rffe_status address rffe a[4:0]: 0x1a reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits swr cfpe cle afpe dfpe rure wure bge reset w ? 0 r ? 0 r ? 0 r ? 0 r ? 0 r ? 0 r ? 0 r ? 0 swr soft ? reset mipi ? rffe registers write ?1? to this bit to reset all the mipi ? rffe registers, except rffe_pm_trig, rffe_group_sid, rffe_usid_0, rffe_usid_1 and rffe_usid_2. this bit will always read ? back ?0?. the soft reset occurs in the last clock cycle of the mipi ? rffe frame which writes ?1? to this bit. right immediately after this frame, all the mipi ? rffe registers have the reset value and are ready to be reprogrammed as desired. the otp duplicated registers below the address 0x1f are reset to the values written in otp. rffe_status bits [6:0] are set ?1? by hardware to flag when a certain condition is detected, as described below. rffe_status bits [6:0] cannot be written, but it is cleared to ?0? under following conditions: ? hardware self ? reset is applied after rffe_status is read ? when swr is written ?1? ? when power mode transitions through startup mode ?01? ? after power ? up reset cfpe 1: command frame with parity error received. on the occurrence of this error, the slave will ignore the entire command sequence cle 1: incompatible command length, due to unexpected ssc received before command length to be completed. on the occurrence of this error, the slave will accept write data up to the last correct and complete frame. when mipi ? rffe multi ? byte read command is detected, the slave will always replay with an extended read command of length of one byte. afpe 1: address frame with parity error received. on the occurrence of this error, the slave will ignore the entire command sequence dfpe 1: data frame with parity error received. on the occurrence of this error, the slave will ignore only the erroneous data byte (s) rure 1: read of non ? existent register was detected. on the occurrence of this error, the slave will not respond to the read command frame. it will keep the bus idle. wure 1: write to non ? existent register was detected. on the occurrence of this error, the slave discards data being written, and on the next received frame, proceeds as normal bge 1: read using the broadcast id was detected on the occurrence of this error, the slave will ignore the entire command sequence tcc ? 303 www. onsemi.com 23 register rffe: rffe_group_sid address rffe a[4:0]: 0x1b reset source: nreset_dig or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits reserved reserved reserved reserved gsid[3] gsid[2] gsid[1] gsid[0] reset 0 0 0 0 w ? 0 w ? 0 w ? 0 w ? 0 gsid = group slave identifier register note: the gsid [3:0] field can be written directly by messages using usid_0, usid_1 or usid_2. note: gsid value is not retained during shutdown power mode. note: gsid value is not affected by swr bit from rffe_status register note: frames using slave address = gsid, can write only to rffe_pm_trig [7:6] and [2:0]. note: rffe read frames containing gsid will be ignored register rffe: rffe_pm_trig address rffe a[4:0]: 0x1c reset source: nreset_dig or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits power mode (note 7) trigger mask 2 (notes 4, 5, 6) trigger mask 1 (notes 4, 5, 6) trigger mask 0 (notes 4, 5, 6) trigger 2 (note 7) trigger 1 (note 7) trigger 0 (note 7) reset w ? 0 w ? 0 w ? 1 w ? 1 w ? 1 w ? 0 w ? 0 w ? 0 4. the trigger mask 2 (bit [5]) can be changed, either set or cleared, only with an individual message using usid_2. the trigger mask 1 (bit [4]) can be changed, either set or cleared, only with an individual message using usid_1. the trigger mask 0 (bit [3]) can be change d, either set or cleared, only with an individual message using usid_0. 5. during broadcast mipi ? rffe accesses using broadcast id or gsid, t rigger bits [2:0] are masked by the pre ? existent setting of trigger mask bits [5:3]. 6. during individual mipi ? rffe accesses, trigger bits [2:0] are masked by the incoming trigger mask bits [5:3] within the same write message to rffe_pm_trig register according to the dac dur configurations. 7. power mode field bits [7:6] and triggers bits [2:0] can be changed by either mipi ? rffe broadcast messages (with gsid or broadcast id slave address). the power mode can be changed by all usid accesses. the trigger bits can be set by individual messages when sla ve address fields within the register write command is are equal to their corresponding control usids. note: none of the 8 bits of rffe_pm_trig register bits are affected by swr bit from rffe_status register. the default reset valu es of the trigger masks are set to ?1? violating the rffe spec, but the trigger at dac write is requested to be the default bit [7:6]: power mode 00: active mode , defined by following hardware behavior: ? boost control active, vhv set by digital interface ? vout a, b, c enabled and controlled by digital interface 01: startup mode , defined by following hardware behavior: ? boost control active, vhv set by digital interface ? vout a, b, c disabled 10: low power mode is defined by following hardware behavior: ? digital interface is active, while all other circuits are in low power mode 11: reserved (state of hardware does not change) bit 5: mask trigger 2 (only usid_2 write access) 0:trigger 2 not masked. the dacs, which are configured in their dur to be controlled by usid_2 have their active registers updated after the trigger 2 is written a value of 1. 1:trigger 2 is masked. the dacs, which are configured in their dur to be controlled by usid_2 have their active registers updated as soon as their new dac values are written in (default). bit 4: mask trigger 1 (only usid_1 write access) 0:trigger 1 not masked. the dacs, which are configured in their dur to be controlled by usid_1 have their active registers updated after the trigger 1 is written a value of 1. 1:trigger 2 is masked. the dacs, which are configured in their dur to be controlled by usid_1 have their active registers updated as soon as their new dac values are written in (default). bit 3: mask trigger 0 (only usid_0 write access) 0:trigger 0 not masked. the dacs, which are configured in their dur to be controlled by usid_0 have their active registers updated after the trigger 0 is written a value of 1. 1:trigger 2 is masked. the dacs, which are configured in their dur to be controlled by usid_0 have their active registers updated as soon as their new dac values are written in (default). tcc ? 303 www. onsemi.com 24 bit 2: trigger 2 (usid_2 or broadcast write access) write 1 to this bit, to move data in dacs, which are configured in their dur under usid_2 control, from shadow registers into active registers. this trigger can be masked by bit 5. the read back of this field returns dacc pending trigger status (from immediate or sw trigger). bit 1: trigger 1 (usid_1 or broadcast write access) write 1 to this bit, to move data in dacs, which are configured in their dur under usid_1 control, from shadow registers into active registers. this trigger can be masked by bit 4. the read back of this field returns dacb pending trigger status (from immediate or sw trigger). bit 0: trigger 0 (usid_0 or broadcast write access) write 1 to this bit, to move data in dacs, which are configured in their dur under usid_0 control, from shadow registers into active registers. this trigger can be masked by bit 3. the read back of this field returns daca pending trigger status (from immediate or sw trigger). register rffe: rffe_product_id address rffe a[4:0]: 0x1d reset source: n/a 7 6 5 4 3 2 1 0 bits pid7 pid6 pid5 pid4 pid3 pid2 pid1 pid0 reset 0 0 0 1 0 0 0 0 bits [7:1] are hardcoded in asic bit [0] depends on version ? 0 for tcc ? 303a product family id history: tcc ? 103a 0 0 0 0 0 1 0 0 tcc ? 106a 0 0 0 0 1 0 0 0 tcc ? 202a 0 0 1 0 0 0 0 0 tcc ? 206a 0 0 1 0 0 1 0 idb0 pin tcc ? 303a 0 0 0 1 0 0 0 0 register rffe: rffe_manufacturer_id address rffe a[4:0]: 0x1e reset source: n/a 7 6 5 4 3 2 1 0 bits mpn7 mpn6 mpn5 mpn4 mpn3 mpn2 mpn1 mpn0 reset 0 0 1 0 1 1 1 0 the 10 mpn bits (mpn0 to mpn9 partially residing under usid registers) are manufacturing id bits unique to on semiconductor. register rffe: rffe_usid_0 (default) address rffe a[4:0]: 0x1f reset source: nreset_dig or swr = ?1? or pwr_mode = ?01? (transition through startup mode) 7 6 5 4 3 2 1 0 bits reserved (2) mpn9 (2) mpn8 (2) usid3 (1) usid2 (1) usid1 (1) usid0 (1) reset 0 0 0 1 w ? 0 w ? 1 w ? 1 w ? 1 usid = unique slave identifier register 1. usid field can be changed by: ? mipi ? rffe broadcast messages when usid field within the register write command is 0b0000 ? mipi ? rffe individual messages when usid field within the register write command equal with content of rffe_reg_0x1f[3:0] 2. in the sequence of writing usid field, the upper [7:4] must match the value 0b0001 hardcoded in the rffe register 0x1f note: usid value is not retained during shutdown power mode. tcc ? 303 www. onsemi.com 25 register 0 write command sequence the command sequence starts with an ssc which is followed by the register 0 write command frame. this frame contains the slave address, a logic one, and the seven bit word that will be written to register 0. the command sequence is depicted below. figure 14. register 0 write command sequence table 16. rffe command frame for register 0 write command sequence description ssc command frame dac configuration 1 0 sa [3,0] 1 0 0 0 0 0 0 0 p bp single register write command sequence the write register command sequence may be used to access each register individually (addresses 0 ? 31). figure 15. single register write command sequence table 17. rffe command frame for register write command sequence for dacs loading proce dure description ssc command frame data frame bp register write dac a 1 0 sa [3, 0] 0 1 0 0 0 1 1 0 p gl_a & dac_a [6:0] p bp register write dac b 1 0 sa [3, 0] 0 1 0 0 0 1 1 1 p gl_b & dac_b [6:0] p bp register write dac c 1 0 sa [3, 0] 0 1 0 0 1 0 0 0 p gl_c & dac_c [6:0] p bp this sequence can be used for read/write procedure for some other purposes as shown on the following table: tcc ? 303 www. onsemi.com 26 table 18. other rffe command sequences description ssc command frame data frame bp active mode 1 0 sa [3, 0] 0 1 0 1 1 1 0 0 p 0 0 x x x x x x p bp startup mode 1 0 sa [3, 0] 0 1 0 1 1 1 0 0 p 0 1 x x x x x x p bp low power 1 0 sa [3, 0] 0 1 0 1 1 1 0 0 p 1 0 x x x x x x p bp reserved 1 0 sa [3, 0] 0 1 0 1 1 1 0 0 p 1 1 x x x x x x p bp product id 1 0 sa [3, 0] 0 1 0 1 1 1 0 1 p 0 0 0 1 0 0 0 0/1 p bp manufacturer id 1 0 sa [3, 0] 0 1 0 1 1 1 1 0 p 0 0 1 0 1 1 1 0 p bp manufacturer usid 1 0 sa [3, 0] 0 1 0 1 1 1 1 1 p 0 0 0 1 usid p bp extended register write command sequence in order to access more than one register in one sequence this message could be used. most commonly it will be used for loading three dac registers at the same time. the four lsbs of the extended register write command frame determine the number of bytes that will be written by the command sequence. a value of 0b0000 would write one byte and a value of 0b1111 would write sixteen bytes. if more than one byte is to be written, the register address in the command sequence contains the address of the first extended register that will be written to and the slave?s local extended register address shall be automatically incremented by one for each byte written up to address 0x1f, starting from the address indicated in the address frame. figure 16. extended register write command sequence tcc ? 303 www. onsemi.com 27 table 19. rffe command frame for extended register write command sequence for dacs loading procedure description ssc command frame address frame data frame bus park tcc ? 303 www. onsemi.com 28 figure 18. extended register read command sequence changing usids changing usid is according to mipi rffe specifications. same manufacturer_id and product_id apply for usid_0/_1/_2. note that usid can be changed with broadcast commands, or commands targeting that particular usid. for example to change usid_0, broadcast commands or commands addressing usid_0 can be used. change usid_0 ? rffe_write_reg 0x1d [0x10 + otp[31]] ? rffe_write_reg 0x1e 0x2e ? rffe_write_reg 0x1f 0x1z, where z is the new usid_0 value change usid_1 ? rffe_write_reg 0x1d [0x10 + otp[31]] ? rffe_write_reg 0x1e 0x2e ? rffe_write_reg 0x18 0x1z, where z is the new usid_1 value change usid_2 ? rffe_write_reg 0x1d [0x10 + otp[31]] ? rffe_write_reg 0x1e 0x2e ? rffe_write_reg 0x19 0x1z, where z is the new usid_2 value tcc ? 303 www. onsemi.com 29 example device operation device setup 1. enable all three dacs ? write 0x07 to register 0x00 2. change vhv voltage to 28 v (default 24 v) ? write 0xdf to register 0x02 change dacs ? change daca voltage to 6.8 v; no glide ? write 0x24 to register 0x06 ? change dacb voltage to 12.0 v; no glide ? write 0x40 to register 0x07 ? change dacc voltage to 0.9 v; no glide ? write 0x05 to register 0x08 setup glide ? set daca glide step duration to 28 s ? write 0x0e to register 0x03 ? set dacb glide step duration to 20 s ? write 0x0a to register 0x04 ? set dacc glide step duration to 42 s ? write 0x15 to register 0x05 change dacs with glide ? keep daca voltage at 6.8 v; glide enabled ? write 0xa4 to register 0x06 (total glide duration is 28 s*256 s = 7168 s); no output change since dac_old = dac_new ? change dacb voltage to 16.4 v; glide enabled ? write 0xd7 to register 0x07 (total glide duration is 20 s*256 s = 5120 s); transitions from 12 v to 16.4 v over 5.12 ms ? change dacc voltage to 20.5 v; glide enabled ? write 0xed to register 0x08 (total glide duration is 42 s*256 s = 10752 us); transitions from 0.9 v to 20.5 v over 10.75 ms note: any sequential registers (eg. 0x03 ? 0x08, as mentioned in setup glide and change dacs with glide sections) can be written with a single extended mipi write, rather than individual write commands. tcc ? 303 www. onsemi.com 30 following picture shows tcc ? 303 and all the necessary external components figure 19. tcc ? 303 with external components table 20. recommended external bom component description nominal value package recommended p/n c boost boost supply capacitor, 10 v 1 f 0402 tdk: c1005x5r1a105k l boost boost inductor 15 h 0603 tdk: vls2010et ? 150m, sunlord sph201610h150mt r filt filtering resistor, 5% 3.3 s 0402 vishay : crcw04023r30jned c vio v io supply decoupling, 10 v 100 nf 0201 murata: grm033r61a104me15d c vdda v vdda supply decoupling, 10 v 1 f 0402 tdk: c1005x5r1a105k c vreg v vreg supply decoupling, 10 v 220 nf 0201 tdk: c0603x5r1a224m c hv boost tank capacitor, 50 v 47 nf 1005 murata: grm155c71h473ke19 c daca,b,c decoupling capacitor, 50 v (note 8) 100 pf 0201 murata: grm0335c1h101jd01d d sch rectifying schottky diode sod ? 923 on semiconductor: nsr0240p2t5g, nsr0340ht1g (note 9), rb521s030t1 (note 9) 8. recommended in noise reduction only ? not essential but place next to ptic if used 9. these devices have not been fully tested; performance cannot be guaranteed. tcc ? 303 www. onsemi.com 31 tape & reel dimensions figure 20. wlcsp carrier tape drawings figure 21. orientation in tape table 21. ordering information device marking package shipping ? tcc ? 303a ? rt t33a rdl (pb ? free) 3000 / tape & reel tcc ? 303b ? rt t33b ?for information on tape and reel specifications, including part orientation and tape sizes, please refer to our tape and reel packaging specifications brochure, brd8011/d. assembly instructions note: it is recommended that under normal circumstances, this device and associated components should be located in a shielded enclosure. tcc ? 303 www. onsemi.com 32 package dimensions wlcsp12, 1.376x1.025x0.68 case 567mw issue a seating plane 0.05 c 0.10 c c side view note 3 a 0.03 c 2x 0.03 c 2x top view e a 0.05 b c 0.03 c 12x b c b a bottom view 123 e/2 e notes: 1. dimensioning and tolerancing per asme y14.5m, 1994. 2. controlling dimension: millimeters. 3. coplanarity applies to the spherical crowns of the solder balls. dim a min max ??? millimeters a1 d 1.376 bsc e b 0.17 0.23 e 0.35 bsc 0.68 0.13 0.19 1.025 bsc 0.17 12x dimensions: millimeters *for additional information on our pb ? free strategy and soldering details, please download the on semiconductor soldering and mounting techniques reference manual, solderrm/d. soldering footprint* 0.35 0.35 recommended package outline pitch pitch a1 d a2 0.38 ref a1 a3 detail a a2 backside coating detail a a3 0.025 ref on semiconductor and are trademarks of semiconductor components industries, llc dba on semiconductor or its subsidiaries i n the united states and/or other countries. on semiconductor owns the rights to a number of patents, trademarks, copyrights, trade secrets, and other intellectual property . a listing of on semiconductor?s product/patent coverage may be accessed at www.onsemi.com/site/pdf/patent ? marking.pdf . on semiconductor reserves the right to make changes without further notice to any products herein. on semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does o n semiconductor assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including wi thout limitation special, consequential or incidental damages. buyer is responsible for its products and applications using on semiconductor products, including compliance with all laws, reg ulations and safety requirements or standards, regardless of any support or applications information provided by on semiconductor. ?typical? parameters which may be provided in on semiconductor data sheets and/or specifications can and do vary in dif ferent applications and actual performance may vary over time. all operating parameters, including ?typic als? must be validated for each customer application by customer?s technical experts. on semiconductor does not convey any license under its patent rights nor the right s of others. on semiconductor products are not designed, intended, or authorized for use as a critical component in life support systems or any fda class 3 medical devices or medical devices with a same or similar classification in a foreign jurisdiction or any devices intended for implantation in the human body. should buyer purchase or use on semicondu ctor products for any such unintended or unauthorized application, buyer shall indemnify and hold on semiconductor and its officers, employees, subsidiaries, affiliates, and distrib utors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that on semiconductor was negligent regarding the design or manufacture of the part. on semiconductor is an equal opportunity/affirmative action employer. this literature is subject to all applicable copyright laws and is not for resale in any manner. publication ordering information n. american technical support : 800 ? 282 ? 9855 toll free usa/canada europe, middle east and africa technical support: phone: 421 33 790 2910 japan customer focus center phone: 81 ? 3 ? 5817 ? 1050 tcc ? 303/d literature fulfillment : literature distribution center for on semiconductor 19521 e. 32nd pkwy, aurora, colorado 80011 usa phone : 303 ? 675 ? 2175 or 800 ? 344 ? 3860 toll free usa/canada fax : 303 ? 675 ? 2176 or 800 ? 344 ? 3867 toll free usa/canada email : orderlit@onsemi.com on semiconductor website : www.onsemi.com order literature : http://www.onsemi.com/orderlit for additional information, please contact your local sales representative ? |
Price & Availability of TCC-303-D
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |